Enhanced traffic indications for multi-link wireless communication devices

ABSTRACT

This disclosure describes systems, methods, and devices related to traffic indications for multi-link devices (MLDs). A device may generate a first traffic indication map (TIM) with a first bitmap including a first indication that traffic is to be sent by a first access point (AP) device of the MLD to a first non-AP device of a second MLD using a first communication link. The device may generate a second TIM with a second bitmap including a second indication that no traffic is to be sent by a second AP device of the MLD to a second non-AP device of the second MLD using a second communication link. The device may send, using the first communication link, the beacon, the beacon including the first TIM and the second TIM. The device may send, using the first communication link, a data frame to the first non-AP device of the second MLD.

TECHNICAL FIELD

This disclosure generally relates to systems and methods for wireless communications and, more particularly, to traffic indications for multi-link devices.

BACKGROUND

Wireless devices are becoming widely prevalent and are increasingly communicating with multiple devices. The Institute of Electrical and Electronics Engineers (IEEE) is developing one or more standards that utilize transmissions between wireless devices.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1A is a network diagram illustrating an example network environment, in accordance with one or more example embodiments of the present disclosure.

FIG. 1B depicts an illustrative schematic diagram for multi-link device (MLD) communications between two logical entities, in accordance with one or more example embodiments of the present disclosure.

FIG. 1C depicts an illustrative schematic diagram for MLD communications between an access point (AP) MLD with logical entities and a non-AP MLD with logical entities, in accordance with one or more example embodiments of the present disclosure.

FIG. 2 depicts an illustrative schematic diagram of MLD communications using a multi-link traffic indication map element, in accordance with one or more example embodiments of the present disclosure.

FIG. 3A illustrates a flow diagram of illustrative process for using a multi-link traffic indication map element, in accordance with one or more example embodiments of the present disclosure.

FIG. 3B illustrates a flow diagram of illustrative process for using a multi-link traffic indication map element, in accordance with one or more example embodiments of the present disclosure.

FIG. 4 illustrates a functional diagram of an exemplary communication station that may be suitable for use as a user device, in accordance with one or more example embodiments of the present disclosure.

FIG. 5 illustrates a block diagram of an example machine upon which any of one or more techniques (e.g., methods) may be performed, in accordance with one or more example embodiments of the present disclosure.

FIG. 6 is a block diagram of a radio architecture in accordance with some examples.

FIG. 7 illustrates an example front-end module circuitry for use in the radio architecture of FIG. 6, in accordance with one or more example embodiments of the present disclosure.

FIG. 8 illustrates an example radio IC circuitry for use in the radio architecture of FIG. 6, in accordance with one or more example embodiments of the present disclosure.

FIG. 9 illustrates an example baseband processing circuitry for use in the radio architecture of FIG. 6, in accordance with one or more example embodiments of the present disclosure.

DETAILED DESCRIPTION

Example embodiments described herein provide certain systems, methods, and devices for traffic indications for multi-link wireless communications devices. The following description and the drawings sufficiently illustrate specific embodiments to enable those skilled in the art to practice them. Other embodiments may incorporate structural, logical, electrical, process, algorithm, and other changes. Portions and features of some embodiments may be included in, or substituted for, those of other embodiments. Embodiments set forth in the claims encompass all available equivalents of those claims.

A station device (STA) may refer to a logical entity that is a singly addressable instance of a medium access control (MAC) and physical layer (PHY) interface to the wireless medium (WM). A communication link (or just “link”) in the context of an IEEE 802.11 medium access control (MAC) entity, may refer to a physical path consisting of exactly one traversal of the wireless medium (WM) that is usable to transfer MAC service data units (MSDUs) between two STAs.

In multi-link communications, a multi-link device (MLD), also referred to as a multi-link logical entity (MLLE), may refer to a device that has more than one affiliated STA and that has a medium access control (MAC) layer (e.g., of a communication layer stack) service access point (SAP) to a logical link control (LLC), which may include a MAC data service. An access point (AP) MLD (A MLD) may refer to an AP device, where each STA affiliated with the STA MLD is an AP. A non-AP ML device (non-AP MLD) maybe an A MLD, where each STA affiliated with the MLD is a non-AP STA. A MLD may be considered a logical/virtual entity with multiple STAs (e.g., AP STAs or non-AP STAs), and each STA concurrently may use separate communication links with corresponding STAs of another MLD. In this manner, a MLD may communicate over multiple communication links.

In some wireless communications, an AP may send beacon frames that provide information to other devices, such as STAs. The beacon frames are specific types of frames defined by the IEEE 802.11 technical standards and may include, for example, a traffic indication map (TIM) that indicates which devices are scheduled to send/receive traffic during the time interval between consecutive respective beacon frames (e.g., a beacon interval). In this manner, a device that is awake to receive a beacon frame may enter a doze state (e.g., power save mode) when the device determines that a TIM indicates no traffic for the device to send or receive during a beacon interval. In particular, a TIM element included in a beacon frame may be used to signal the presence of buffered data at the AP for its associated STAs (e.g., STAs that have performed an association process with the AP). Respective bit positions of the Partial Virtual Bitmap subfield in the TIM element (also referred to as a TIM bitmap) may correspond to specific device address (e.g., an association identifier—AID) and may be set to 1 when there is buffered data for the STA that has the AID corresponding to the bit position.

However, because MLDs with multiple logical entities may communicate using multiple different links (e.g., different frequency bands), device power may be wasted by requiring the multiple logical entities (e.g., logical STAs on a non-AP MLD) of a physical MLD to be awake to receive respective beacons sent across the respective links used by the MLD. In this manner, the physical non-AP MLD may need to be awake for multiple beacons sent across multiple links, preventing the non-AP MLD from being in a doze state. In addition, because traditional STAs use distinct AIDs to distinguish from one another, an AP-MLD sending a TIM in a beacon frame may waste time and resources looking up different AIDs for the different logical entities of a non-AP MLD to indicate whether the respective logical entities are to send/receive traffic during a beacon interval.

There is therefore a need for enhanced traffic indications for MLDs.

In one or more embodiments, the use of traffic indications for MLDs may enable MLD Wi-Fi communications between logical entities of MLDs to improve latency and throughput. An A-MLD may have multiple logical AP entities, each of which may use a respective link (e.g., in a different frequency band) to communicate with a respective logical non-AP entity of one or multiple non-AP MLDs. For example, a first logical AP entity of an A-MLD may communicate with a first logical non-AP entity of a first non-AP MLD and with a first logical non-AP entity of a second non-AP MLD using a first frequency band. A second logical AP entity of the A-MLD may communicate with a second logical non-AP entity of the first non-AP MLD and with a second logical non-AP entity of the second non-AP MLD using a different second frequency band. The first logical AP entity of the A-MLD may send first beacons to the first logical non-AP entities of the first and second non-AP MLDs using the first frequency band, and the second logical AP entity of the A-MLD may send second beacons to the second logical non-AP entities of the first and second non-AP MLDs using the second frequency band. Instead of the first and second logical non-AP entities of the first and second non-AP MLDs both needing to be awake to receive both the first and second beacons, the first logical AP entity of the A-MLD may use the first beacons to communicate TIM information for the second logical non-AP entities of the first and second non-AP MLDs, thereby allowing the second logical non-AP entities of the first and second non-AP MLDs to remain in a doze state (e.g., even when the second beacons are sent) until the first beacons indicate that the second logical non-AP entities of the first and second non-AP MLDs need to be awake in the second frequency band to send/receive traffic (e.g., as indicated by the TIM in the first beacons sent in the first frequency band).

In one or more embodiments, the first beacons used for MLDs may include both TIM information for the logical non-AP entities of the first and second non-AP MLDs operating in the first frequency band in which the first beacons are sent and may include an additional TIM element, referred to as a ML-TIM element for each frequency band used by the logical entities of the A-MLD. Each ML-TIM element may be for a specific frequency band and may communicate to the non-AP MLDs using the frequency band whether the respective logical non-AP entities of the non-AP MLDs operating in the frequency band have traffic to send/receive using the indicated frequency band during a beacon interval in the first frequency band. Therefore, for N frequency bands used by the AP MLD, the beacons may include one TIM and N−1 ML-TIMs. Such TIM element piggybacking may be useful especially for non-concurrent (e.g., single radio) non-AP MLD devices because it may help avoid frequent link switching and/or wake-ups to receive separate beacon frames in each link.

In one or more embodiments, MLD beacons (e.g., the first and second beacons described above) may include the MLD-TIM element format shown below in Table 1.

TABLE 1 MLD-TIM Element Format. Element ID Length Band ID DTIM Count DTIM Period Bitmap Control Partial Virtual Bitmap 1 octet 1 octet 1 octet 1 octet 1 octet 1 octet 1-251 octets

The new fields in the ML-TIM that currently are not included in legacy beacons (e.g., in a legacy TIM), as shown in Table 1, are the Element ID field and the Band field. The Element ID field may be encoded (e.g., using a currently reserved value of legacy beacons) to indicate a ML-TIM. The Band ID (or Link ID) field may be added to legacy beacons to identify the target frequency band for which the ML-TIM is applicable. The length field, the delivery TIM (DTIM) Count field, the DTIM Period field, the Bitmap Control field, and the Partial Virtual Bitmap field fields are currently defined by the IEEE 802.11 technical standards for legacy beacons. The Partial Virtual Bitmap field may include the sequence of 0 and 1 bits for the logical non-AP STAs that use the frequency band indicated by the Band ID field. For example, a first logical non-AP STA of a first non-AP MLD may be assigned the first bit position of the Partial Virtual Bitmap field, and a first logical non-AP STA of a second non-AP MLD may be assigned the second bit position of the Partial Virtual Bitmap field. In particular, a 0 indicates that no traffic is available for the logical non-AP STA assigned to the bit position where the 0 is, and a 1 indicates that traffic is available for the logical non-AP STA assigned to the bit position where the 1 is. For example, a Partial Virtual Bitmap field of 010 indicates that no traffic is available for the logical non-AP STA assigned to first the bit position, that traffic is available for the logical non-AP STA assigned to second the bit position, and that no traffic is available for the logical non-AP STA assigned to third the bit position. The indication of whether traffic is available for a logical non-AP STA applies to one beacon interval—the interval of time between the beacon that includes the indication and the next (e.g., subsequent beacon), meaning that a logical non-AP entity in one frequency band (e.g., indicated by the Band ID field) may determine whether to be awake during a beacon interval between beacons sent in a different frequency band. The proposed mechanism may simplify the TIM bitmap construction and applicable regardless of the address allocation scheme for allocating association identifiers (AIDs) per non-AP MLDs or per STA (or link).

In legacy beacons, the TIM conveys the information of current operating band (e.g., the frequency band in which the beacon is sent). In one or more embodiments, beacons for MLDs may include the TIM to indicate traffic for the frequency band in which the beacon is sent, and may include a respective ML-TIM for any additional links (e.g., frequency band) used by the A-MLD that sends the beacons. In addition, some methods of using a ML-TIM may require each AP to track per-link AID information, thereby requiring additional computational steps (e.g., additional table lookup operations) in a ML-TIM bitmap construction procedure, which may cause additional MAC-layer delay in ML-TIM element construction for use cases such as dynamic load balancing. Instead, the A-MLD may avoid needing to look up each AID (or other address) of the logical non-AP entities of non-AP MLDs and may rely on the Link ID field. In this manner, because each bit position of the Partial Virtual Bitmap field corresponds to the AID of a device (or logical entity), the same AID may be used for all logical entities of a non-AP MLD.

In one or more embodiments, the mapping of TIM bitmaps to AIDs may be the same for all of the ML-TIM and regular TIM elements conveyed in a beacon. Therefore, there may be no need for each AP logical entity to track per-link AID information for each non-AP MLD device, making it easy and fast to construct a TIM bitmap for ML-TIM elements. For example, when an AP logical entity in link 1 decides to send buffered data to a STA logical entity in link 2, then the AP logical entity merely needs to set the bit location corresponding to the current AID (in link 1) to “1” in TIM bitmap in ML-TIM element for link 2 (and set it to “0” for the current link in regular TIM element). It may be assumed that STA logical entities in non-AP MLD are assigned different AIDs per link, the proposed method also works for the case where non-AP MLLE device is allocated a single AID for all of its STAs (or links). This may eliminate the need for allocating per-link AIDs (e.g., at least from the TIM bitmap construction perspective).

In one or more embodiments, the ML-TIM of a beacon for MLDs may cascade subfields of a TIM to communicate the ML-TIMs of multiple frequency bands. In this manner, a beacon sent by an A-MLD in one frequency band may include ML-TIMs for other frequency bands used by the A-MLD. As shown above in Table 1, the beacon may include a Band ID, Bitmap Control, and Partial Virtual Bitmap for any frequency band. To communicate the traffic in multiple frequency bands, a single beacon may cascade some fields as shown below in Table 2.

TABLE 2 ML-TIM Element Format for Beacons. Element Bitmap Partial Virtual Bitmap Partial Virtual Element ID Link ID Control Bitmap Link ID Control Bitmap ID Length Extension (e.g., Link X) (e.g., for Link X) (e.g., for Link X) (e.g., Link Y) (e.g., for Link Y) (e.g., for Link Y) 1 octet 1 octet 0 or 1 octet 1 octet 1 octet 1-251 octet 1 octet 1 octet 1-251 octet

As shown in Table 2 above, each frequency band (e.g., Link X, Link Y, etc.) may be indicated by a Link ID (or Band ID) of the beacon, and may have its own respective Bitmap Control and Partial Virtual Bitmap. Such cascading may improve MAC efficiency because the first three subfields (i.e., “Element ID”, “Length” and “Extended ID”) may appear only once in the beacon and do not need to be repeated for each link (or for each ML-TIM element). In this manner, when a non-AP MLD receives a beacon with the elements of Table 2, the non-AP MLD may determine whether a first non-AP logical entity of the non-AP MLD needs to be awake in a first frequency band (e.g., Link X) to send/receive traffic, and whether a second non-AP logical entity of the non-AP MLD needs to be awake in a second frequency band (e.g., Link Y) to send/receive traffic, and may activate and doze the logical entities accordingly.

The above descriptions are for purposes of illustration and are not meant to be limiting. Numerous other examples, configurations, processes, algorithms, etc., may exist, some of which are described in greater detail below. Example embodiments will now be described with reference to the accompanying figures.

FIG. 1A is a network diagram illustrating an example network environment, according to some example embodiments of the present disclosure. Wireless network 100 may include one or more user devices 120 and one or more access points(s) (AP) 102, which may communicate in accordance with IEEE 802.11 communication standards. The user device(s) 120 may be mobile devices that are non-stationary (e.g., not having fixed locations) or may be stationary devices.

In some embodiments, the user devices 120 and the AP 102 may include one or more computer systems similar to that of the functional diagram of FIG. 4 and/or the example machine/system of FIG. 5.

One or more illustrative user device(s) 120 and/or AP(s) 102 may be operable by one or more user(s) 110. It should be noted that any addressable unit may be a station (STA). An STA may take on multiple distinct characteristics, each of which shape its function. For example, a single addressable unit might simultaneously be a portable STA, a quality-of-service (QoS) STA, a dependent STA, and a hidden STA. The one or more illustrative user device(s) 120 and the AP(s) 102 may be STAs. The one or more illustrative user device(s) 120 and/or AP(s) 102 may operate as a personal basic service set (PBSS) control point/access point (PCP/AP). The user device(s) 120 (e.g., 124, 126, or 128) and/or AP(s) 102 may include any suitable processor-driven device including, but not limited to, a mobile device or a non-mobile, e.g., a static, device. For example, user device(s) 120 and/or AP(s) 102 may include, a user equipment (UE), a station (STA), an access point (AP), a software enabled AP (SoftAP), a personal computer (PC), a wearable wireless device (e.g., bracelet, watch, glasses, ring, etc.), a desktop computer, a mobile computer, a laptop computer, an ultrabook™ computer, a notebook computer, a tablet computer, a server computer, a handheld computer, a handheld device, an internet of things (IoT) device, a sensor device, a PDA device, a handheld PDA device, an on-board device, an off-board device, a hybrid device (e.g., combining cellular phone functionalities with PDA device functionalities), a consumer device, a vehicular device, a non-vehicular device, a mobile or portable device, a non-mobile or non-portable device, a mobile phone, a cellular telephone, a PCS device, a PDA device which incorporates a wireless communication device, a mobile or portable GPS device, a DVB device, a relatively small computing device, a non-desktop computer, a “carry small live large” (CSLL) device, an ultra mobile device (UMD), an ultra mobile PC (UMPC), a mobile internet device (MID), an “origami” device or computing device, a device that supports dynamically composable computing (DCC), a context-aware device, a video device, an audio device, an A/V device, a set-top-box (STB), a blu-ray disc (BD) player, a BD recorder, a digital video disc (DVD) player, a high definition (HD) DVD player, a DVD recorder, a HD DVD recorder, a personal video recorder (PVR), a broadcast HD receiver, a video source, an audio source, a video sink, an audio sink, a stereo tuner, a broadcast radio receiver, a flat panel display, a personal media player (PMP), a digital video camera (DVC), a digital audio player, a speaker, an audio receiver, an audio amplifier, a gaming device, a data source, a data sink, a digital still camera (DSC), a media player, a smartphone, a television, a music player, or the like. Other devices, including smart devices such as lamps, climate control, car components, household components, appliances, etc. may also be included in this list.

As used herein, the term “Internet of Things (IoT) device” is used to refer to any object (e.g., an appliance, a sensor, etc.) that has an addressable interface (e.g., an Internet protocol (IP) address, a Bluetooth identifier (ID), a near-field communication (NFC) ID, etc.) and can transmit information to one or more other devices over a wired or wireless connection. An IoT device may have a passive communication interface, such as a quick response (QR) code, a radio-frequency identification (RFID) tag, an NFC tag, or the like, or an active communication interface, such as a modem, a transceiver, a transmitter-receiver, or the like. An IoT device can have a particular set of attributes (e.g., a device state or status, such as whether the IoT device is on or off, open or closed, idle or active, available for task execution or busy, and so on, a cooling or heating function, an environmental monitoring or recording function, a light-emitting function, a sound-emitting function, etc.) that can be embedded in and/or controlled/monitored by a central processing unit (CPU), microprocessor, ASIC, or the like, and configured for connection to an IoT network such as a local ad-hoc network or the Internet. For example, IoT devices may include, but are not limited to, refrigerators, toasters, ovens, microwaves, freezers, dishwashers, dishes, hand tools, clothes washers, clothes dryers, furnaces, air conditioners, thermostats, televisions, light fixtures, vacuum cleaners, sprinklers, electricity meters, gas meters, etc., so long as the devices are equipped with an addressable communications interface for communicating with the IoT network. IoT devices may also include cell phones, desktop computers, laptop computers, tablet computers, personal digital assistants (PDAs), etc. Accordingly, the IoT network may be comprised of a combination of “legacy” Internet-accessible devices (e.g., laptop or desktop computers, cell phones, etc.) in addition to devices that do not typically have Internet-connectivity (e.g., dishwashers, etc.).

The user device(s) 120 and/or AP(s) 102 may also include mesh stations in, for example, a mesh network, in accordance with one or more IEEE 802.11 standards and/or 3GPP standards.

Any of the user device(s) 120 (e.g., user devices 124, 126, 128), and AP(s) 102 may be configured to communicate with each other via one or more communications networks 130 and/or 135 wirelessly or wired. The user device(s) 120 may also communicate peer-to-peer or directly with each other with or without the AP(s) 102. Any of the communications networks 130 and/or 135 may include, but not limited to, any one of a combination of different types of suitable communications networks such as, for example, broadcasting networks, cable networks, public networks (e.g., the Internet), private networks, wireless networks, cellular networks, or any other suitable private and/or public networks. Further, any of the communications networks 130 and/or 135 may have any suitable communication range associated therewith and may include, for example, global networks (e.g., the Internet), metropolitan area networks (MANs), wide area networks (WANs), local area networks (LANs), or personal area networks (PANs). In addition, any of the communications networks 130 and/or 135 may include any type of medium over which network traffic may be carried including, but not limited to, coaxial cable, twisted-pair wire, optical fiber, a hybrid fiber coaxial (HFC) medium, microwave terrestrial transceivers, radio frequency communication mediums, white space communication mediums, ultra-high frequency communication mediums, satellite communication mediums, or any combination thereof.

Any of the user device(s) 120 (e.g., user devices 124, 126, 128) and AP(s) 102 may include one or more communications antennas. The one or more communications antennas may be any suitable type of antennas corresponding to the communications protocols used by the user device(s) 120 (e.g., user devices 124, 126 and 128), and AP(s) 102. Some non-limiting examples of suitable communications antennas include Wi-Fi antennas, Institute of Electrical and Electronics Engineers (IEEE) 802.11 family of standards compatible antennas, directional antennas, non-directional antennas, dipole antennas, folded dipole antennas, patch antennas, multiple-input multiple-output (MIMO) antennas, omnidirectional antennas, quasi-omnidirectional antennas, or the like. The one or more communications antennas may be communicatively coupled to a radio component to transmit and/or receive signals, such as communications signals to and/or from the user devices 120 and/or AP(s) 102.

Any of the user device(s) 120 (e.g., user devices 124, 126, 128), and AP(s) 102 may be configured to perform directional transmission and/or directional reception in conjunction with wirelessly communicating in a wireless network. Any of the user device(s) 120 (e.g., user devices 124, 126, 128), and AP(s) 102 may be configured to perform such directional transmission and/or reception using a set of multiple antenna arrays (e.g., DMG antenna arrays or the like). Each of the multiple antenna arrays may be used for transmission and/or reception in a particular respective direction or range of directions. Any of the user device(s) 120 (e.g., user devices 124, 126, 128), and AP(s) 102 may be configured to perform any given directional transmission towards one or more defined transmit sectors. Any of the user device(s) 120 (e.g., user devices 124, 126, 128), and AP(s) 102 may be configured to perform any given directional reception from one or more defined receive sectors.

MIMO beamforming in a wireless network may be accomplished using RF beamforming and/or digital beamforming. In some embodiments, in performing a given MIMO transmission, user devices 120 and/or AP(s) 102 may be configured to use all or a subset of its one or more communications antennas to perform MIMO beamforming.

Any of the user devices 120 (e.g., user devices 124, 126, 128), and AP(s) 102 may include any suitable radio and/or transceiver for transmitting and/or receiving radio frequency (RF) signals in the bandwidth and/or channels corresponding to the communications protocols utilized by any of the user device(s) 120 and AP(s) 102 to communicate with each other. The radio components may include hardware and/or software to modulate and/or demodulate communications signals according to pre-established transmission protocols. The radio components may further have hardware and/or software instructions to communicate via one or more Wi-Fi and/or Wi-Fi direct protocols, as standardized by the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standards. In certain example embodiments, the radio component, in cooperation with the communications antennas, may be configured to communicate via 2.4 GHz channels (e.g. 802.11b, 802.11g, 802.11n, 802.11ax), 5 GHz channels (e.g. 802.11n, 802.11ac, 802.11ax), or 60 GHZ channels (e.g. 802.11ad, 802.11ay). 800 MHz channels (e.g. 802.11ah). The communications antennas may operate at 28 GHz and 40 GHz. It should be understood that this list of communication channels in accordance with certain 802.11 standards is only a partial list and that other 802.11 standards may be used (e.g., Next Generation Wi-Fi, or other standards). In some embodiments, non-Wi-Fi protocols may be used for communications between devices, such as Bluetooth, dedicated short-range communication (DSRC), Ultra-High Frequency (UHF) (e.g. IEEE 802.11af, IEEE 802.22), white band frequency (e.g., white spaces), or other packetized radio communications. The radio component may include any known receiver and baseband suitable for communicating via the communications protocols. The radio component may further include a low noise amplifier (LNA), additional signal amplifiers, an analog-to-digital (A/D) converter, one or more buffers, and digital baseband.

In one embodiment, and with reference to FIG. 1A, AP 102 may communicate with one or more user devices 120. The AP 102 may send beacons 142 to the one or more user devices 120, and the AP 102 and the one or more user devices 120 may send and receive data frames 144 to each other. The beacons 142 may include TIMs 146 to indicate to the one or more user devices 120 whether there is traffic for the one or more user devices 120 in between respective beacons 142.

It is understood that the above descriptions are for purposes of illustration and are not meant to be limiting.

FIG. 1B depicts an illustrative schematic diagram for MLD communications between two logical entities, in accordance with one or more example embodiments of the present disclosure.

Referring to FIG. 1B, there are shown two MLDs in communication with each other. MLD 151 may include multiple STAs (e.g., STA 152, STA 154, STA 156, etc.), and MLD 160 may include multiple STAs (e.g., STA 162, STA 164, STA 166, etc.). The STAs of the MLD 151 and the STAs of the MLD 160 may set up links with each other (e.g., link 167 for a first frequency band used by the STA 152 and the STA 162, link 168 for a second frequency band used by the STA 154 and the STA 164, link 169 for a second frequency band used by the STA 156 and the STA 166). In this example of FIG. 1B, the two MLDs may be two separate physical devices, where each one comprises a number of virtual or logical devices (e.g., the STAs).

FIG. 1C depicts an illustrative schematic diagram for MLD communications between an AP MLD with logical entities and a non-AP MLD with logical entities, in accordance with one or more example embodiments of the present disclosure.

Referring to FIG. 1C, there are shown two MLDs on either side, each which includes multiple STAs that can set up links with each other. For infrastructure framework, MLD 172 may be an A-MLD with logical APs (e.g., AP 174, AP 176, and AP 178) on one side, and MLD 180 may be a non-AP MLD including non-AP logical entities (non-AP STA 182, non-AP STA 184, and non-AP STA 186) on the other side. The detailed definition is shown below. It should be noted that the term MLLE and MLD are interchangeable and indicate the same type of entity. Throughout this disclosure, MLLE may be used but anywhere the MLLE term is used, it can be replaced with MLD. Multi-link non-AP logical entity (non-AP MLLE, also can be referred to as non-AP MLD): A multi-link logical entity, where each STA within the multi-link logical entity is a non-AP EHT STA. it should be noted that this framework is a natural extension from the one link operation between two STAs, which are AP and non-AP STA under the infrastructure framework (e.g., when an AP is used as a medium for communication between STAs).

In the example of FIG. 1C, the MLD 172 and the MLD 180 may be two separate physical devices, where each one comprises a number of virtual or logical devices. For example, the multi-link AP logical entity may comprise three APs, AP 174 operating on 2.4 GHz (e.g., link 188), AP 176 operating on 5 GHz (e.g., link 190), and AP 178 operating on 6 GHz (e.g., link 192). Further, the multi-link non-AP logical entity may comprise three non-AP STAs, non-AP STA 182 communicating with AP 174 on link 188, non-AP STA 184 communicating with AP 176 on link 190, and non-AP STA 186 communicating with AP 178 on link 192.

The MLD 172 is shown in FIG. 1C to have access to a distribution system (DS), which is a system used to interconnect a set of BSSs to create an extended service set (ESS). The MLD 172 is also shown in FIG. 1C to have access a distribution system medium (DSM), which is the medium used by a DS for BSS interconnections. Simply put, DS and DSM allow the AP to communicate with different BSSs.

It should be understood that although the example shows three logical entities within the MLD 172 and the three logical entities within the MLD 180, this is merely for illustration purposes and that other numbers of logical entities with each of the MLDs may be envisioned.

FIG. 2 depicts an illustrative schematic diagram of MLD communications using a ML-TIM element, in accordance with one or more example embodiments of the present disclosure.

Referring to FIG. 2, an A-MLD that includes multiple logical AP entities (e.g., AP 204, AP 206, etc.) may communicate with a non-AP MLD 208 that includes multiple logical non-AP entities (e.g., STA 210, STA 212, etc.). The AP 204 may communicate with the STA 210 using a first link 214 (e.g., using a first frequency band). The AP 206 may communicate with the STA 212 using a second link 216 (e.g., using a second frequency band). The AP 204 may send beacons using the first link 214, and the AP 206 may send beacons using the second link 216. While the non-AP MLD 208 is the only non-AP MLD shown, other non-AP MLDs with respective non-AP logical entities may communicate with the A-MLD 202 using the first link 214 and the second link 216 (e.g., the beacons sent using the first link 214 and the second link 216 may be received by multiple non-AP MLDs). In particular, the AP 204 may send a beacon 218 followed by a beacon 220 using the first link 214. The time interval between the beacon 218 and the beacon 220 may be referred to as a beacon interval 222. The beacon 218 may indicate the beacon interval 222, allowing the STA 210 to activate from a doze state in time to receive the beacon 220. The beacon 220 may indicate whether non-AP MLDs using the first link 214 and the second link 216 have traffic to send/receive during a time period between the beacon 220 and the next beacon 224 to be sent using the first link 214 (e.g., during beacon interval 226). During beacon interval 226, the AP 204 and the STA 210 may exchange (e.g., send and/or receive) frames (e.g., data frame 228, data frame 230, etc.). In this manner, the non-AP MLD 208 may keep the STA 210 active in the first link 214 during the beacon interval 226, and to receive the next beacon (e.g., beacon 224). In this example, the beacon 224 may indicate no traffic for the STA 210 using the first link 214 during a time period between the beacon 224 and a next beacon 232 (e.g., during beacon interval 234), so the STA 210 may enter a doze state during the beacon interval 234.

Still referring to FIG. 2, beacons sent by the AP 206 using the second link 216 may be sent at different times than the beacons sent using the first link 214. To avoid the need for the non-AP MLD 208 to activate the STA 212 in the second link 216 to receive beacons in the second link 216, the beacons in the first link 214 may indicate whether traffic is available for the STA 212 in the second link 216 during a respective beacon interval between beacons sent in the first link 214. In this manner, the STA 212 may be in a doze state when beacons are sent using the second link 216, but may wake up during a respective beacon interval between beacons sent in the first link 214 to send/receive traffic using the second link 216. For example, the AP 206 may send beacon 240 and later beacon 242, and the STA 212 may doze during the beacon interval 244 between the beacon 240 and the beacon 242 because the beacon 220 in the link 214 may indicate no traffic for the STA 212 during the beacon interval 226. However, because the beacon 224 may indicate traffic for the STA 212 during the beacon interval 234, the non-AP MLD 208 may wake up the STA 212 after the STA 210 receives the beacon 224 and may allow the STA 210 to enter a doze state during the beacon interval 234 (e.g., because the beacon 224 may indicate no traffic for the STA 210 during the beacon interval 234). The STA 212 then may exchange frames (e.g., data frame 250, data frame 252, etc.) with the AP 206 using the second link 216 during the beacon interval 234, after which the STA 212 may reenter a doze state (e.g., even when the AP 206 sends a next beacon 246, resulting in beacon interval 248).

Still referring to FIG. 2, the beacons may include both a TIM and one or more ML-TIMs. For example, the beacon 220 may include TIM 260 (e.g., indicating traffic for the first link 214) and a ML-TIM 262 (e.g., indicating traffic for the second link 216). While not shown, the beacon 220 may include additional ML-TIMs for any additional links used by the A-MLD 202. The TIM 260 may include a TIM bitmap 264 of 0s and 1s indicating, for a respective device/entity assigned the bit location of the TIM bitmap 264, that the device/entity has traffic in the first link 214 during the beacon interval 226. For example, when the STA 210 is assigned the third bit location of the TIM bitmap 264, and the TIM bitmap 264 is 00101 . . . , the non-AP MLD 208 may determine that the AP 204 has traffic for the STA 210 using the first link 214 during the beacon interval 226. The ML-TIM 262 may include a Link ID field 266 (e.g., the Band ID field of Table 1 or Table 2) to identify the link (e.g., the second link 216) to which a TIM bitmap 268 applies. Using the example of the AID for the non-AP MLD 208 using the third bit location of the TIM bitmap 268, when the TIM bitmap 268 is 00001 . . . , the non-AP MLD 208 may determine that the AP 206 does not have traffic for the STA 212 using the second link 216 during the beacon interval 226. In this manner, the non-AP MLD 208 may allow the STA 212 to be in doze state during the beacon interval 226. In this manner, the STA 212 does not need to be awake to receive the beacon 242 in the second link 216 to determine whether there is traffic for the STA 212 during the beacon interval 248.

Still referring to FIG. 2, the beacon 224 may include both a TIM and one or more ML-TIMs. For example, the beacon 224 may include TIM 270 (e.g., indicating traffic for the first link 214) and a ML-TIM 272 (e.g., indicating traffic for the second link 216). While not shown, the beacon 224 may include additional ML-TIMs for any additional links used by the A-MLD 202. The TIM 270 may include a TIM bitmap 274 of 0s and 1s indicating, for a respective device/entity assigned the bit location of the TIM bitmap 274, that the device/entity has traffic in the first link 214 during the beacon interval 234. For example, when the STA 210 is assigned the third bit location of the TIM bitmap 274, and the TIM bitmap 274 is 00001 . . . , the non-AP MLD 208 may determine that the AP 204 does not has traffic for the STA 210 using the first link 214 during the beacon interval 234, and may allow the STA 210 to doze during the beacon interval 234. The ML-TIM 272 may include a Link ID field 276 (e.g., the Band ID field of Table 1 or Table 2) to identify the link (e.g., the second link 216) to which a TIM bitmap 278 applies. Using the example of the AID for the STA 210 using the third bit location of the TIM bitmap 278, when the TIM bitmap 278 is 00101 . . . , the non-AP MLD 208 may determine that the AP 206 has traffic for the STA 212 using the second link 216 during the beacon interval 234. In this manner, the non-AP MLD 208 may switch from the first link 214 to the second link 216 and cause the STA 212 to be awake during the beacon interval 234.

In one or more embodiments, when the non-AP MLD 208 determines that downlink traffic is available from the A-MLD 202 to a STA of the non-AP MLD 208, the STA to receive the downlink traffic may send an uplink frame (e.g., a power-save poll frame, a trigger frame, etc.) to the A-MLD 202 to indicate that the STA is ready to receive the downlink traffic. In this manner, although not shown, the uplink frame, while not shown, may occur before the exchange of data frames during a beacon interval.

One of the advantages of multi-link communication is the flexibility in utilizing multiple available links, and multi-link APs dynamically may allocate links for downlink/uplink transmission. For example, in case the AP 204 decides to switch its operating link for downlink transmission from the first link 214 to the second link 216 for dynamic load balancing, latency reduction, etc., then the AP 204 simply may flip the values of bit location corresponding to the AID for the current link: “1”→“0” for the first link 214 and “0”→“1” for the second link 216, without needing identify (e.g., look up) the corresponding AID for the second link 216 and/or re-constructing the entire TIM bitmap for the second link 216 (e.g., if the bit location corresponding to an AID was not included in the original TIM bitmap).

It is understood that the above descriptions are for purposes of illustration and are not meant to be limiting.

FIG. 3A illustrates a flow diagram of illustrative process 300 for using a multi-link traffic indication map element, in accordance with one or more example embodiments of the present disclosure.

At block 302, a device (e.g., the A-MLD 202 of FIG. 2) may generate a first TIM for non-AP devices (e.g., STA 210 of FIG. 2) of one or more MLDs (e.g., the non-AP MLD 208 of FIG. 2) using a first frequency band (e.g., the first link 214 of FIG. 2). The first TIM may be a regular (e.g., legacy) TIM without a Band ID, indicating traffic for respective STAs of non-AP MLDs connected to a first AP device (e.g., AP 204 of FIG. 2) of the device using the first frequency band. The TIM may indicate whether traffic is to be sent by the first AP device to a respective non-AP STA of a non-AP MLD during a beacon interval and using the first frequency band. The bitmap for the TIM is described above with respect to FIG. 2.

At block 304, the device may generate one or more additional TIMs for non-AP devices (e.g., STA 212 of FIG. 2) of the one or more MLDs (e.g., the non-AP MLD 208 of FIG. 2) using a respective frequency band (e.g., the second link 216 of FIG. 2) different than the first frequency band, each additional TIM indicated by a respective Band ID. The one or more additional TIMs may be ML-TIMs, indicating traffic for respective STAs of non-AP MLDs connected to a respective AP device (e.g., AP 206 of FIG. 2) of the device using the frequency band indicated by the Band ID. The one or more additional TIMs may indicate whether traffic is to be sent by a respective AP device to a respective non-AP STA of a non-AP MLD during a beacon interval and using the frequency band indicated by the corresponding Band ID. The bitmaps for the ML-TIMs are described above with respect to FIG. 2.

At block 306, the device may generate a beacon that includes the first TIM and the one or more additional TIMs. In this manner, a single beacon sent in the first frequency band may include TIMs for devices using one or more other frequency bands, allowing the receiving devices to determine which frequency bands in which to be active, and which frequency bands in which to doze during a given beacon interval. At block 308, the device may cause the AP device to send the beacon using the first frequency band.

At block 310, the device may cause the first AP device of the device to send data frames in the first frequency band (e.g., the data frames 228 and 230 of FIG. 2) according to the non-AP devices that are to receive traffic as indicated by the first TIM. At block 312, the device may cause the respective AP devices of the device to send data frames in the one or more additional frequency bands as indicated by the one or more additional TIMs.

At block 314, the device may cause the APs of the device to send additional beacons, any of which may include a TIM for the frequency band in which a beacon is sent and one or more additional TIMs for other frequency bands used by the device.

FIG. 3B illustrates a flow diagram of illustrative process 350 for using a multi-link traffic indication map element, in accordance with one or more example embodiments of the present disclosure.

At block 352, a device (e.g., the non-AP MLD 208 of FIG. 2) may identify, with a first non-AP device (e.g., the STA 210 of FIG. 2) a first beacon (e.g., beacon 220 of FIG. 2) received from a first AP device (e.g., AP 204 of FIG. 2) using a first frequency band (e.g., the first link 214 of FIG. 2). The non-AP device of the device that receives the first beacon may be awake in the first frequency band to receive the first beacon.

At block 354, the device may identify a first TIM in the first beacon. The first TIM may be a regular (e.g., legacy) TIM without a Band ID, indicating traffic for respective STAs of non-AP MLDs connected to a first AP device (e.g., AP 204 of FIG. 2) that sent the first beacon. The first TIM may indicate whether traffic is to be sent by the first AP device to a respective non-AP STA of a non-AP MLD during a beacon interval and using the first frequency band. The bitmap for the TIM is described above with respect to FIG. 2.

At block 356, the device may identify one or more additional TIMs in the first beacon. The one or more additional TIMs may be ML-TIMs, indicating traffic for respective STAs of non-AP MLDs connected to a respective AP device (e.g., AP 206 of FIG. 2) of the device using the frequency band indicated by the Band ID. The one or more additional TIMs may indicate whether traffic is to be sent by a respective AP device to a respective non-AP STA of a non-AP MLD during a beacon interval and using the frequency band indicated by the corresponding Band ID. The bitmaps for the ML-TIMs are described above with respect to FIG. 2.

At block 358, the device may manage power save modes based on the TIMs in the beacon. For example, when the device determines that a TIM corresponding to a respective frequency band indicates that traffic is present for the device in that frequency band, the device may activate or keep awake the STA device using that frequency band. When the device determines that a TIM corresponding to a respective frequency band indicates that traffic is present for the device in that frequency band, the device may cause its STA device using that frequency band to enter a doze state.

At block 360, the device may identify a data frame during the beacon interval, received based on the TIMs in the first beacon. In particular, the corresponding AP device using the frequency band may send one or more data frames in that frequency band to the STAs identified in the TIM corresponding to the frequency band.

At block 362, the device may identify additional beacons from one or more AP devices in one or more respective frequency bands. An additional beacon may include a TIM for the frequency band in which the beacon was sent, and one or more additional TIMs for other frequency bands.

It is understood that the above descriptions are for purposes of illustration and are not meant to be limiting.

FIG. 4 shows a functional diagram of an exemplary communication station 400 in accordance with some embodiments. In one embodiment, FIG. 4 illustrates a functional block diagram of a communication station that may be suitable for use as an AP 102 (FIG. 1A) or user device 120 (FIG. 1A) in accordance with some embodiments. The communication station 700 may also be suitable for use as a handheld device, a mobile device, a cellular telephone, a smartphone, a tablet, a netbook, a wireless terminal, a laptop computer, a wearable computer device, a femtocell, a high data rate (HDR) subscriber station, an access point, an access terminal, or other personal communication system (PCS) device.

The communication station 400 may include communications circuitry 402 and a transceiver 410 for transmitting and receiving signals to and from other communication stations using one or more antennas 401. The communications circuitry 402 may include circuitry that can operate the physical layer (PHY) communications and/or medium access control (MAC) communications for controlling access to the wireless medium, and/or any other communications layers for transmitting and receiving signals. The communication station 400 may also include processing circuitry 406 and memory 408 arranged to perform the operations described herein. In some embodiments, the communications circuitry 402 and the processing circuitry 406 may be configured to perform operations detailed in FIGS. 1-3.

In accordance with some embodiments, the communications circuitry 402 may be arranged to contend for a wireless medium and configure frames or packets for communicating over the wireless medium. The communications circuitry 402 may be arranged to transmit and receive signals. The communications circuitry 402 may also include circuitry for modulation/demodulation, upconversion/downconversion, filtering, amplification, etc. In some embodiments, the processing circuitry 406 of the communication station 400 may include one or more processors. In other embodiments, two or more antennas 401 may be coupled to the communications circuitry 402 arranged for sending and receiving signals. The memory 408 may store information for configuring the processing circuitry 406 to perform operations for configuring and transmitting message frames and performing the various operations described herein. The memory 408 may include any type of memory, including non-transitory memory, for storing information in a form readable by a machine (e.g., a computer). For example, the memory 408 may include a computer-readable storage device, read-only memory (ROM), random-access memory (RAM), magnetic disk storage media, optical storage media, flash-memory devices and other storage devices and media.

In some embodiments, the communication station 400 may be part of a portable wireless communication device, such as a personal digital assistant (PDA), a laptop or portable computer with wireless communication capability, a web tablet, a wireless telephone, a smartphone, a wireless headset, a pager, an instant messaging device, a digital camera, an access point, a television, a medical device (e.g., a heart rate monitor, a blood pressure monitor, etc.), a wearable computer device, or another device that may receive and/or transmit information wirelessly.

In some embodiments, the communication station 400 may include one or more antennas 401. The antennas 401 may include one or more directional or omnidirectional antennas, including, for example, dipole antennas, monopole antennas, patch antennas, loop antennas, microstrip antennas, or other types of antennas suitable for transmission of RF signals. In some embodiments, instead of two or more antennas, a single antenna with multiple apertures may be used. In these embodiments, each aperture may be considered a separate antenna. In some multiple-input multiple-output (MIMO) embodiments, the antennas may be effectively separated for spatial diversity and the different channel characteristics that may result between each of the antennas and the antennas of a transmitting station.

In some embodiments, the communication station 400 may include one or more of a keyboard, a display, a non-volatile memory port, multiple antennas, a graphics processor, an application processor, speakers, and other mobile device elements. The display may be an LCD screen including a touch screen.

Although the communication station 400 is illustrated as having several separate functional elements, two or more of the functional elements may be combined and may be implemented by combinations of software-configured elements, such as processing elements including digital signal processors (DSPs), and/or other hardware elements. For example, some elements may include one or more microprocessors, DSPs, field-programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), radio-frequency integrated circuits (RFICs) and combinations of various hardware and logic circuitry for performing at least the functions described herein. In some embodiments, the functional elements of the communication station 400 may refer to one or more processes operating on one or more processing elements.

Certain embodiments may be implemented in one or a combination of hardware, firmware, and software. Other embodiments may also be implemented as instructions stored on a computer-readable storage device, which may be read and executed by at least one processor to perform the operations described herein. A computer-readable storage device may include any non-transitory memory mechanism for storing information in a form readable by a machine (e.g., a computer). For example, a computer-readable storage device may include read-only memory (ROM), random-access memory (RAM), magnetic disk storage media, optical storage media, flash-memory devices, and other storage devices and media. In some embodiments, the communication station 400 may include one or more processors and may be configured with instructions stored on a computer-readable storage device memory.

FIG. 5 illustrates a block diagram of an example of a machine 500 or system upon which any one or more of the techniques (e.g., methodologies) discussed herein may be performed. In other embodiments, the machine 500 may operate as a standalone device or may be connected (e.g., networked) to other machines. In a networked deployment, the machine 500 may operate in the capacity of a server machine, a client machine, or both in server-client network environments. In an example, the machine 500 may act as a peer machine in peer-to-peer (P2P) (or other distributed) network environments. The machine 500 may be a personal computer (PC), a tablet PC, a set-top box (STB), a personal digital assistant (PDA), a mobile telephone, a wearable computer device, a web appliance, a network router, a switch or bridge, or any machine capable of executing instructions (sequential or otherwise) that specify actions to be taken by that machine, such as a base station. Further, while only a single machine is illustrated, the term “machine” shall also be taken to include any collection of machines that individually or jointly execute a set (or multiple sets) of instructions to perform any one or more of the methodologies discussed herein, such as cloud computing, software as a service (SaaS), or other computer cluster configurations.

Examples, as described herein, may include or may operate on logic or a number of components, modules, or mechanisms. Modules are tangible entities (e.g., hardware) capable of performing specified operations when operating. A module includes hardware. In an example, the hardware may be specifically configured to carry out a specific operation (e.g., hardwired). In another example, the hardware may include configurable execution units (e.g., transistors, circuits, etc.) and a computer readable medium containing instructions where the instructions configure the execution units to carry out a specific operation when in operation. The configuring may occur under the direction of the executions units or a loading mechanism. Accordingly, the execution units are communicatively coupled to the computer-readable medium when the device is operating. In this example, the execution units may be a member of more than one module. For example, under operation, the execution units may be configured by a first set of instructions to implement a first module at one point in time and reconfigured by a second set of instructions to implement a second module at a second point in time.

The machine (e.g., computer system) 500 may include a hardware processor 502 (e.g., a central processing unit (CPU), a graphics processing unit (GPU), a hardware processor core, or any combination thereof), a main memory 504 and a static memory 506, some or all of which may communicate with each other via an interlink (e.g., bus) 508. The machine 500 may further include a power management device 532, a graphics display device 510, an alphanumeric input device 512 (e.g., a keyboard), and a user interface (UI) navigation device 514 (e.g., a mouse). In an example, the graphics display device 510, alphanumeric input device 512, and UI navigation device 514 may be a touch screen display. The machine 500 may additionally include a storage device (i.e., drive unit) 516, a signal generation device 518 (e.g., a speaker), an enhanced traffic device 519, a network interface device/transceiver 520 coupled to antenna(s) 530, and one or more sensors 528, such as a global positioning system (GPS) sensor, a compass, an accelerometer, or other sensor. The machine 500 may include an output controller 534, such as a serial (e.g., universal serial bus (USB), parallel, or other wired or wireless (e.g., infrared (IR), near field communication (NFC), etc.) connection to communicate with or control one or more peripheral devices (e.g., a printer, a card reader, etc.)). The operations in accordance with one or more example embodiments of the present disclosure may be carried out by a baseband processor. The baseband processor may be configured to generate corresponding baseband signals. The baseband processor may further include physical layer (PHY) and medium access control layer (MAC) circuitry, and may further interface with the hardware processor 502 for generation and processing of the baseband signals and for controlling operations of the main memory 504, the storage device 516, and/or the enhanced traffic device 519. The baseband processor may be provided on a single radio card, a single chip, or an integrated circuit (IC).

The storage device 516 may include a machine readable medium 522 on which is stored one or more sets of data structures or instructions 524 (e.g., software) embodying or utilized by any one or more of the techniques or functions described herein. The instructions 524 may also reside, completely or at least partially, within the main memory 504, within the static memory 506, or within the hardware processor 502 during execution thereof by the machine 500. In an example, one or any combination of the hardware processor 502, the main memory 504, the static memory 506, or the storage device 516 may constitute machine-readable media.

The enhanced traffic device 519 may carry out or perform any of the operations and processes (e.g., process 300 of FIG. 3A, process 350 of FIG. 3B) described and shown above.

It is understood that the above are only a subset of what the enhanced traffic device 519 may be configured to perform and that other functions included throughout this disclosure may also be performed by the enhanced traffic device 519.

While the machine-readable medium 522 is illustrated as a single medium, the term “machine-readable medium” may include a single medium or multiple media (e.g., a centralized or distributed database, and/or associated caches and servers) configured to store the one or more instructions 524.

Various embodiments may be implemented fully or partially in software and/or firmware. This software and/or firmware may take the form of instructions contained in or on a non-transitory computer-readable storage medium. Those instructions may then be read and executed by one or more processors to enable performance of the operations described herein. The instructions may be in any suitable form, such as but not limited to source code, compiled code, interpreted code, executable code, static code, dynamic code, and the like. Such a computer-readable medium may include any tangible non-transitory medium for storing information in a form readable by one or more computers, such as but not limited to read only memory (ROM); random access memory (RAM); magnetic disk storage media; optical storage media; a flash memory, etc.

The term “machine-readable medium” may include any medium that is capable of storing, encoding, or carrying instructions for execution by the machine 500 and that cause the machine 500 to perform any one or more of the techniques of the present disclosure, or that is capable of storing, encoding, or carrying data structures used by or associated with such instructions. Non-limiting machine-readable medium examples may include solid-state memories and optical and magnetic media. In an example, a massed machine-readable medium includes a machine-readable medium with a plurality of particles having resting mass. Specific examples of massed machine-readable media may include non-volatile memory, such as semiconductor memory devices (e.g., electrically programmable read-only memory (EPROM), or electrically erasable programmable read-only memory (EEPROM)) and flash memory devices; magnetic disks, such as internal hard disks and removable disks; magneto-optical disks; and CD-ROM and DVD-ROM disks.

The instructions 524 may further be transmitted or received over a communications network 526 using a transmission medium via the network interface device/transceiver 520 utilizing any one of a number of transfer protocols (e.g., frame relay, internet protocol (IP), transmission control protocol (TCP), user datagram protocol (UDP), hypertext transfer protocol (HTTP), etc.). Example communications networks may include a local area network (LAN), a wide area network (WAN), a packet data network (e.g., the Internet), mobile telephone networks (e.g., cellular networks), plain old telephone (POTS) networks, wireless data networks (e.g., Institute of Electrical and Electronics Engineers (IEEE) 802.11 family of standards known as Wi-Fi®, IEEE 802.16 family of standards known as WiMax®), IEEE 802.15.4 family of standards, and peer-to-peer (P2P) networks, among others. In an example, the network interface device/transceiver 520 may include one or more physical jacks (e.g., Ethernet, coaxial, or phone jacks) or one or more antennas to connect to the communications network 526. In an example, the network interface device/transceiver 520 may include a plurality of antennas to wirelessly communicate using at least one of single-input multiple-output (SIMO), multiple-input multiple-output (MIMO), or multiple-input single-output (MISO) techniques. The term “transmission medium” shall be taken to include any intangible medium that is capable of storing, encoding, or carrying instructions for execution by the machine 500 and includes digital or analog communications signals or other intangible media to facilitate communication of such software. The operations and processes described and shown above may be carried out or performed in any suitable order as desired in various implementations. Additionally, in certain implementations, at least a portion of the operations may be carried out in parallel. Furthermore, in certain implementations, less than or more than the operations described may be performed.

The word “exemplary” is used herein to mean “serving as an example, instance, or illustration.” Any embodiment described herein as “exemplary” is not necessarily to be construed as preferred or advantageous over other embodiments. The terms “computing device,” “user device,” “communication station,” “station,” “handheld device,” “mobile device,” “wireless device” and “user equipment” (UE) as used herein refers to a wireless communication device such as a cellular telephone, a smartphone, a tablet, a netbook, a wireless terminal, a laptop computer, a femtocell, a high data rate (HDR) subscriber station, an access point, a printer, a point of sale device, an access terminal, or other personal communication system (PCS) device. The device may be either mobile or stationary.

As used within this document, the term “communicate” is intended to include transmitting, or receiving, or both transmitting and receiving. This may be particularly useful in claims when describing the organization of data that is being transmitted by one device and received by another, but only the functionality of one of those devices is required to infringe the claim. Similarly, the bidirectional exchange of data between two devices (both devices transmit and receive during the exchange) may be described as “communicating,” when only the functionality of one of those devices is being claimed. The term “communicating” as used herein with respect to a wireless communication signal includes transmitting the wireless communication signal and/or receiving the wireless communication signal. For example, a wireless communication unit, which is capable of communicating a wireless communication signal, may include a wireless transmitter to transmit the wireless communication signal to at least one other wireless communication unit, and/or a wireless communication receiver to receive the wireless communication signal from at least one other wireless communication unit.

As used herein, unless otherwise specified, the use of the ordinal adjectives “first,” “second,” “third,” etc., to describe a common object, merely indicates that different instances of like objects are being referred to and are not intended to imply that the objects so described must be in a given sequence, either temporally, spatially, in ranking, or in any other manner.

The term “access point” (AP) as used herein may be a fixed station. An access point may also be referred to as an access node, a base station, an evolved node B (eNodeB), or some other similar terminology known in the art. An access terminal may also be called a mobile station, user equipment (UE), a wireless communication device, or some other similar terminology known in the art. Embodiments disclosed herein generally pertain to wireless networks. Some embodiments may relate to wireless networks that operate in accordance with one of the IEEE 802.11 standards.

Some embodiments may be used in conjunction with various devices and systems, for example, a personal computer (PC), a desktop computer, a mobile computer, a laptop computer, a notebook computer, a tablet computer, a server computer, a handheld computer, a handheld device, a personal digital assistant (PDA) device, a handheld PDA device, an on-board device, an off-board device, a hybrid device, a vehicular device, a non-vehicular device, a mobile or portable device, a consumer device, a non-mobile or non-portable device, a wireless communication station, a wireless communication device, a wireless access point (AP), a wired or wireless router, a wired or wireless modem, a video device, an audio device, an audio-video (A/V) device, a wired or wireless network, a wireless area network, a wireless video area network (WVAN), a local area network (LAN), a wireless LAN (WLAN), a personal area network (PAN), a wireless PAN (WPAN), and the like.

Some embodiments may be used in conjunction with one way and/or two-way radio communication systems, cellular radio-telephone communication systems, a mobile phone, a cellular telephone, a wireless telephone, a personal communication system (PCS) device, a PDA device which incorporates a wireless communication device, a mobile or portable global positioning system (GPS) device, a device which incorporates a GPS receiver or transceiver or chip, a device which incorporates an RFID element or chip, a multiple input multiple output (MIMO) transceiver or device, a single input multiple output (SIMO) transceiver or device, a multiple input single output (MISO) transceiver or device, a device having one or more internal antennas and/or external antennas, digital video broadcast (DVB) devices or systems, multi-standard radio devices or systems, a wired or wireless handheld device, e.g., a smartphone, a wireless application protocol (WAP) device, or the like.

Some embodiments may be used in conjunction with one or more types of wireless communication signals and/or systems following one or more wireless communication protocols, for example, radio frequency (RF), infrared (IR), frequency-division multiplexing (FDM), orthogonal FDM (OFDM), time-division multiplexing (TDM), time-division multiple access (TDMA), extended TDMA (E-TDMA), general packet radio service (GPRS), extended GPRS, code-division multiple access (CDMA), wideband CDMA (WCDMA), CDMA 2000, single-carrier CDMA, multi-carrier CDMA, multi-carrier modulation (MDM), discrete multi-tone (DMT), Bluetooth®, global positioning system (GPS), Wi-Fi, Wi-Max, ZigBee, ultra-wideband (UWB), global system for mobile communications (GSM), 2G, 2.5G, 3G, 3.5G, 4G, fifth generation (5G) mobile networks, 3GPP, long term evolution (LTE), LTE advanced, enhanced data rates for GSM Evolution (EDGE), or the like. Other embodiments may be used in various other devices, systems, and/or networks.

Example 1 may be a device comprising memory and processing circuitry configured to: generate a first traffic indication map (TIM) comprising a first bitmap comprising a first indication that traffic is to be sent by a first access point (AP) device of the MLD to a first non-AP device of a second MLD during a beacon interval occurring after a beacon using a first communication link between the first AP device of the MLD and the first non-AP device of the second MLD; generate a second TIM comprising a second bitmap comprising a second indication that no traffic is to be sent by a second AP device of the MLD to a second non-AP device of the second MLD during the beacon interval using a second communication link between the second AP device of the MLD and the second non-AP device of the second MLD; cause to send, using the first AP device of the MLD and the first communication link, the beacon, the beacon comprising the first TIM and the second TIM; and cause to send, using the first AP device of the MLD and the first communication link, a data frame to the first non-AP device of the second MLD during the beacon interval.

Example 2 may include the device of example 1 and/or some other example herein, wherein the processing circuitry is further configured to: generate a third TIM comprising a third bitmap comprising a third indication that no traffic is to be sent by the first AP device of the MLD to the first non-AP device of the second MLD during a second beacon interval occurring after a second beacon using the first communication link; generate a fourth TIM comprising a fourth bitmap comprising a fourth indication that traffic is to be sent by the second AP device of the MLD to the second non-AP device of the second MLD during the second beacon interval using the second communication link; cause to send, using the first AP device of the MLD and the first communication link, the second beacon, the second beacon comprising the first TIM and the second TIM; and cause to send, using the first AP device of the MLD and the first communication link, a data frame to the first non-AP device of the second MLD during the second beacon interval.

Example 3 may include the device of example 2 and/or some other example herein, wherein: a first link identifier indicative of the first communication link is absent from the first TIM and the third TIM, the second TIM comprises a second link identifier indicative of the second communication link, and the fourth TIM comprises the second link identifier.

Example 4 may include the device of example 1 and/or some other example herein, wherein the second indication is associated with a doze state for the second non-AP device during the beacon interval.

Example 5 may include the device of example 1 and/or some other example herein, wherein the first indication is a first bit associated with an association identifier for the first non-AP device of the second MLD, and wherein the second indication is a second bit associated with the association identifier for the first non-AP device of the second MLD.

Example 6 may include the device of example 1 and/or some other example herein, wherein the processing circuitry is further configured to: generate a third TIM comprising a third bitmap comprising a third indication that no traffic is to be sent by a third AP device of the MLD to a third non-AP device of the second MLD during the beacon interval using a third communication link between the third AP device of the MLD and the third non-AP device of the second MLD, wherein the beacon further comprises the third TIM.

Example 7 may include the device of example 1 and/or some other example herein, wherein the processing circuitry is further configured to cause to send a second beacon using the second AP device of the MLD and the second communication link during the beacon interval.

Example 8 may include the device of example 1 and/or some other example herein, further comprising a transceiver configured to transmit and receive wireless signals comprising at least one of the beacon or the data frame.

Example 9 may include the device of example 8 and/or some other example herein, further comprising an antenna coupled to the transceiver to cause to send the wireless signals.

Example 10 may include a non-transitory computer-readable medium storing computer-executable instructions which when executed by one or more processors result in performing operations comprising: identifying, by a first non-access point (AP) device of a first MLD, a beacon received from a first AP device of a second MLD using a first communication link between the first non-AP device of the first MLD and the first AP device of the second MLD; identifying, by the first MLD, a first traffic indication map (TIM) in the beacon, the first TIM comprising a first bitmap comprising a first indication that traffic is to be sent by the first AP device of the second MLD to the first non-AP device of the first MLD during a beacon interval occurring after the beacon using the first communication link; identifying, by the first MLD, a second TIM in the beacon, the second TIM comprising a second bitmap comprising a second indication that no traffic is to be sent by a second AP device of the second MLD to a second non-AP device of the first MLD during the beacon interval using a second communication link between the second AP device of the second MLD and the second non-AP device of the first MLD; causing, by the first MLD, the second non-AP device of the first MLD to enter a doze state during the beacon interval; and identifying, by the first MLD, a data frame received during the beacon interval from the first AP device of the second MLD using the first communication link.

Example 11 may include the non-transitory computer-readable medium of example 10 and/or some other example herein, the operations further comprising: identifying, by the first MLD, a second beacon received from the first AP device of the second MLD using the first communication link; identifying, by the first MLD, a third TIM in the second beacon, the third TIM comprising a third bitmap comprising a third indication that no traffic is to be sent by the first AP device of the second MLD to the first non-AP device of the first MLD during a second beacon interval occurring after the second beacon using the first communication link; identifying, by the first MLD, a fourth TIM in the second beacon, the fourth TIM comprising a fourth indication that traffic is to be sent by the second AP device of the second MLD to the second non-AP device of the first MLD during the second beacon interval using the second communication link; causing, by the first MLD, the first non-AP device of the first MLD to enter a doze state during the second beacon interval; and identifying, by the first MLD, a data frame received during the second beacon interval from the second AP device of the second MLD using the first communication link.

Example 12 may include the non-transitory computer-readable medium of example 10 and/or some other example herein, wherein: a first link identifier indicative of the first communication link is absent from the first TIM and the third TIM, the second TIM comprises a second link identifier indicative of the second communication link, and the fourth TIM comprises the second link identifier.

Example 13 may include the non-transitory computer-readable medium of example 10 and/or some other example herein, wherein the first indication is a first bit associated with an association identifier for the first non-AP device of the first MLD, and wherein the second indication is a second bit associated with the association identifier for the first non-AP device of the first MLD.

Example 14 may include the non-transitory computer-readable medium of example 10 and/or some other example herein, the operations further comprising: identifying, by the first MLD, a third TIM in the beacon, the third TIM comprising a third bitmap comprising a third indication that no traffic is to be sent by a third AP device of the second MLD to a third non-AP device of the first MLD during the beacon interval using a third communication link between the third AP device of the second MLD and the third non-AP device of the first MLD; and causing, by the first MLD, the third non-AP device of the first MLD to enter a doze state during the beacon interval.

Example 15 may include a method for indicating traffic using multi-link devices (MLDs), the method comprising: generating, by processing circuitry of a first MLD, a first traffic indication map (TIM) comprising a first bitmap comprising a first indication that traffic is to be sent by a first access point (AP) device of the first MLD to a first non-AP device of a second MLD during a beacon interval occurring after a beacon using a first communication link between the first AP device of the first MLD and the first non-AP device of the second MLD; generating, by the processing circuitry, a second TIM comprising a second bitmap comprising a second indication that no traffic is to be sent by a second AP device of the first MLD to a second non-AP device of the second MLD during the beacon interval using a second communication link between the second AP device of the first MLD and the second non-AP device of the second MLD; causing to send, by the processing circuitry, using the first AP device of the first MLD and the first communication link, the beacon, the beacon comprising the first TIM and the second TIM; and causing to send, by the processing circuitry, using the first AP device of the first MLD and the first communication link, a data frame to the first non-AP device of the second MLD during the beacon interval.

Example 16 may include the method of example 15 and/or some other example herein, further comprising: generating a third TIM comprising a third bitmap comprising a third indication that no traffic is to be sent by the first AP device of the first MLD to the first non-AP device of the second MLD during a second beacon interval occurring after a second beacon using the first communication link; generating a fourth TIM comprising a fourth bitmap comprising a fourth indication that traffic is to be sent by the second AP device of the first MLD to the second non-AP device of the second MLD during the second beacon interval using the second communication link; causing to send, using the first AP device of the first MLD and the first communication link, the second beacon, the second beacon comprising the first TIM and the second TIM; and cause to send, using the first AP device of the first MLD and the first communication link, a data frame to the first non-AP device of the second MLD during the second beacon interval.

Example 17 may include the method of example 15 and/or some other example herein, wherein: a first link identifier indicative of the first communication link is absent from the first TIM and the third TIM, the second TIM comprises a second link identifier indicative of the second communication link, and the fourth TIM comprises the second link identifier.

Example 18 may include the method of example 15 and/or some other example herein, wherein the second indication is associated with a doze state for the second non-AP device during the beacon interval.

Example 19 may include the method of example 15 and/or some other example herein, wherein the first indication is a first bit associated with an association identifier for the first non-AP device of the second MLD, and wherein the second indication is a second bit associated with the association identifier for the first non-AP device of the second MLD.

Example, 20 may include the method of example 15 and/or some other example herein, further comprising: generating a third TIM comprising a third bitmap comprising a third indication that no traffic is to be sent by a third AP device of the first MLD to a third non-AP device of the second MLD during the beacon interval using a third communication link between the third AP device of the first MLD and the third non-AP device of the second MLD, wherein the beacon further comprises the third TIM.

Example 21 may include an apparatus comprising means for: generating a first traffic indication map (TIM) comprising a first bitmap comprising a first indication that traffic is to be sent by a first access point (AP) device of a first MLD to a first non-AP device of a second MLD during a beacon interval occurring after a beacon using a first communication link between the first AP device of the first MLD and the first non-AP device of the second MLD; generating a second TIM comprising a second bitmap comprising a second indication that no traffic is to be sent by a second AP device of the first MLD to a second non-AP device of the second MLD during the beacon interval using a second communication link between the second AP device of the first MLD and the second non-AP device of the second MLD; causing to send, using the first AP device of the first MLD and the first communication link, the beacon, the beacon comprising the first TIM and the second TIM; and causing to send, using the first AP device of the first MLD and the first communication link, a data frame to the first non-AP device of the second MLD during the beacon interval.

Example 22 may include one or more non-transitory computer-readable media comprising instructions to cause an electronic device, upon execution of the instructions by one or more processors of the electronic device, to perform one or more elements of a method described in or related to any of examples 1-21, or any other method or process described herein

Example 23 may include an apparatus comprising logic, modules, and/or circuitry to perform one or more elements of a method described in or related to any of examples 1-21, or any other method or process described herein.

Example 24 may include a method, technique, or process as described in or related to any of examples 1-21, or portions or parts thereof.

Example 25 may include an apparatus comprising: one or more processors and one or more computer readable media comprising instructions that, when executed by the one or more processors, cause the one or more processors to perform the method, techniques, or process as described in or related to any of examples 1-21, or portions thereof.

Example 26 may include a method of communicating in a wireless network as shown and described herein.

Example 27 may include a system for providing wireless communication as shown and described herein.

Example 28 may include a device for providing wireless communication as shown and described herein.

Embodiments according to the disclosure are in particular disclosed in the attached claims directed to a method, a storage medium, a device and a computer program product, wherein any feature mentioned in one claim category, e.g., method, can be claimed in another claim category, e.g., system, as well. The dependencies or references back in the attached claims are chosen for formal reasons only. However, any subject matter resulting from a deliberate reference back to any previous claims (in particular multiple dependencies) can be claimed as well, so that any combination of claims and the features thereof are disclosed and can be claimed regardless of the dependencies chosen in the attached claims. The subject-matter which can be claimed comprises not only the combinations of features as set out in the attached claims but also any other combination of features in the claims, wherein each feature mentioned in the claims can be combined with any other feature or combination of other features in the claims. Furthermore, any of the embodiments and features described or depicted herein can be claimed in a separate claim and/or in any combination with any embodiment or feature described or depicted herein or with any of the features of the attached claims.

The foregoing description of one or more implementations provides illustration and description, but is not intended to be exhaustive or to limit the scope of embodiments to the precise form disclosed. Modifications and variations are possible in light of the above teachings or may be acquired from practice of various embodiments.

Certain aspects of the disclosure are described above with reference to block and flow diagrams of systems, methods, apparatuses, and/or computer program products according to various implementations. It will be understood that one or more blocks of the block diagrams and flow diagrams, and combinations of blocks in the block diagrams and the flow diagrams, respectively, may be implemented by computer-executable program instructions. Likewise, some blocks of the block diagrams and flow diagrams may not necessarily need to be performed in the order presented, or may not necessarily need to be performed at all, according to some implementations.

These computer-executable program instructions may be loaded onto a special-purpose computer or other particular machine, a processor, or other programmable data processing apparatus to produce a particular machine, such that the instructions that execute on the computer, processor, or other programmable data processing apparatus create means for implementing one or more functions specified in the flow diagram block or blocks. These computer program instructions may also be stored in a computer-readable storage media or memory that may direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable storage media produce an article of manufacture including instruction means that implement one or more functions specified in the flow diagram block or blocks. As an example, certain implementations may provide for a computer program product, comprising a computer-readable storage medium having a computer-readable program code or program instructions implemented therein, said computer-readable program code adapted to be executed to implement one or more functions specified in the flow diagram block or blocks. The computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational elements or steps to be performed on the computer or other programmable apparatus to produce a computer-implemented process such that the instructions that execute on the computer or other programmable apparatus provide elements or steps for implementing the functions specified in the flow diagram block or blocks.

Accordingly, blocks of the block diagrams and flow diagrams support combinations of means for performing the specified functions, combinations of elements or steps for performing the specified functions and program instruction means for performing the specified functions. It will also be understood that each block of the block diagrams and flow diagrams, and combinations of blocks in the block diagrams and flow diagrams, may be implemented by special-purpose, hardware-based computer systems that perform the specified functions, elements or steps, or combinations of special-purpose hardware and computer instructions.

Conditional language, such as, among others, “can,” “could,” “might,” or “may,” unless specifically stated otherwise, or otherwise understood within the context as used, is generally intended to convey that certain implementations could include, while other implementations do not include, certain features, elements, and/or operations. Thus, such conditional language is not generally intended to imply that features, elements, and/or operations are in any way required for one or more implementations or that one or more implementations necessarily include logic for deciding, with or without user input or prompting, whether these features, elements, and/or operations are included or are to be performed in any particular implementation.

Many modifications and other implementations of the disclosure set forth herein will be apparent having the benefit of the teachings presented in the foregoing descriptions and the associated drawings. Therefore, it is to be understood that the disclosure is not to be limited to the specific implementations disclosed and that modifications and other implementations are intended to be included within the scope of the appended claims. Although specific terms are employed herein, they are used in a generic and descriptive sense only and not for purposes of limitation.

FIG. 9 is a block diagram of a radio architecture 105A, 105B in accordance with some embodiments that may be implemented in any one of the example AP 102 and/or the example user device(s)120 of FIG. 1A. Radio architecture 105A, 105B may include radio front-end module (FEM) circuitry 904 a-b, radio IC circuitry 906 a-b and baseband processing circuitry 908 a-b. Radio architecture 105A, 105B as shown includes both Wireless Local Area Network (WLAN) functionality and Bluetooth (BT) functionality although embodiments are not so limited. In this disclosure, “WLAN” and “Wi-Fi” are used interchangeably.

FEM circuitry 904 a-b may include a WLAN or Wi-Fi FEM circuitry 904 a and a Bluetooth (BT) FEM circuitry 904 b. The WLAN FEM circuitry 904 a may include a receive signal path comprising circuitry configured to operate on WLAN RF signals received from one or more antennas 901, to amplify the received signals and to provide the amplified versions of the received signals to the WLAN radio IC circuitry 906 a for further processing. The BT FEM circuitry 904 b may include a receive signal path which may include circuitry configured to operate on BT RF signals received from one or more antennas 901, to amplify the received signals and to provide the amplified versions of the received signals to the BT radio IC circuitry 906 b for further processing. FEM circuitry 904 a may also include a transmit signal path which may include circuitry configured to amplify WLAN signals provided by the radio IC circuitry 906 a for wireless transmission by one or more of the antennas 901. In addition, FEM circuitry 904 b may also include a transmit signal path which may include circuitry configured to amplify BT signals provided by the radio IC circuitry 906 b for wireless transmission by the one or more antennas. In the embodiment of FIG. 9, although FEM 904 a and FEM 904 b are shown as being distinct from one another, embodiments are not so limited, and include within their scope the use of an FEM (not shown) that includes a transmit path and/or a receive path for both WLAN and BT signals, or the use of one or more FEM circuitries where at least some of the FEM circuitries share transmit and/or receive signal paths for both WLAN and BT signals.

Radio IC circuitry 906 a-b as shown may include WLAN radio IC circuitry 906 a and BT radio IC circuitry 906 b. The WLAN radio IC circuitry 906 a may include a receive signal path which may include circuitry to down-convert WLAN RF signals received from the FEM circuitry 904 a and provide baseband signals to WLAN baseband processing circuitry 908 a. BT radio IC circuitry 906 b may in turn include a receive signal path which may include circuitry to down-convert BT RF signals received from the FEM circuitry 904 b and provide baseband signals to BT baseband processing circuitry 908 b. WLAN radio IC circuitry 906 a may also include a transmit signal path which may include circuitry to up-convert WLAN baseband signals provided by the WLAN baseband processing circuitry 908 a and provide WLAN RF output signals to the FEM circuitry 904 a for subsequent wireless transmission by the one or more antennas 901. BT radio IC circuitry 906 b may also include a transmit signal path which may include circuitry to up-convert BT baseband signals provided by the BT baseband processing circuitry 908 b and provide BT RF output signals to the FEM circuitry 904 b for subsequent wireless transmission by the one or more antennas 901. In the embodiment of FIG. 9, although radio IC circuitries 906 a and 906 b are shown as being distinct from one another, embodiments are not so limited, and include within their scope the use of a radio IC circuitry (not shown) that includes a transmit signal path and/or a receive signal path for both WLAN and BT signals, or the use of one or more radio IC circuitries where at least some of the radio IC circuitries share transmit and/or receive signal paths for both WLAN and BT signals.

Baseband processing circuity 908 a-b may include a WLAN baseband processing circuitry 908 a and a BT baseband processing circuitry 908 b. The WLAN baseband processing circuitry 908 a may include a memory, such as, for example, a set of RAM arrays in a Fast Fourier Transform or Inverse Fast Fourier Transform block (not shown) of the WLAN baseband processing circuitry 908 a. Each of the WLAN baseband circuitry 908 a and the BT baseband circuitry 908 b may further include one or more processors and control logic to process the signals received from the corresponding WLAN or BT receive signal path of the radio IC circuitry 906 a-b, and to also generate corresponding WLAN or BT baseband signals for the transmit signal path of the radio IC circuitry 906 a-b. Each of the baseband processing circuitries 908 a and 908 b may further include physical layer (PHY) and medium access control layer (MAC) circuitry, and may further interface with a device for generation and processing of the baseband signals and for controlling operations of the radio IC circuitry 906 a-b.

Referring still to FIG. 9, according to the shown embodiment, WLAN-BT coexistence circuitry 913 may include logic providing an interface between the WLAN baseband circuitry 908 a and the BT baseband circuitry 908 b to enable use cases requiring WLAN and BT coexistence. In addition, a switch 903 may be provided between the WLAN FEM circuitry 904 a and the BT FEM circuitry 904 b to allow switching between the WLAN and BT radios according to application needs. In addition, although the antennas 901 are depicted as being respectively connected to the WLAN FEM circuitry 904 a and the BT FEM circuitry 904 b, embodiments include within their scope the sharing of one or more antennas as between the WLAN and BT FEMs, or the provision of more than one antenna connected to each of FEM 904 a or 904 b.

In some embodiments, the front-end module circuitry 904 a-b, the radio IC circuitry 906 a-b, and baseband processing circuitry 908 a-b may be provided on a single radio card, such as wireless radio card 902. In some other embodiments, the one or more antennas 901, the FEM circuitry 904 a-b and the radio IC circuitry 906 a-b may be provided on a single radio card. In some other embodiments, the radio IC circuitry 906 a-b and the baseband processing circuitry 908 a-b may be provided on a single chip or integrated circuit (IC), such as IC 912.

In some embodiments, the wireless radio card 902 may include a WLAN radio card and may be configured for Wi-Fi communications, although the scope of the embodiments is not limited in this respect. In some of these embodiments, the radio architecture 105A, 105B may be configured to receive and transmit orthogonal frequency division multiplexed (OFDM) or orthogonal frequency division multiple access (OFDMA) communication signals over a multicarrier communication channel. The OFDM or OFDMA signals may comprise a plurality of orthogonal subcarriers.

In some of these multicarrier embodiments, radio architecture 105A, 105B may be part of a Wi-Fi communication station (STA) such as a wireless access point (AP), a base station or a mobile device including a Wi-Fi device. In some of these embodiments, radio architecture 105A, 105B may be configured to transmit and receive signals in accordance with specific communication standards and/or protocols, such as any of the Institute of Electrical and Electronics Engineers (IEEE) standards including, 802.11n-2009, IEEE 802.11-2012, IEEE 802.11-2016, 802.11n-2009, 802.11ac, 802.11ah, 802.11ad, 802.11ay and/or 802.11ax standards and/or proposed specifications for WLANs, although the scope of embodiments is not limited in this respect. Radio architecture 105A, 105B may also be suitable to transmit and/or receive communications in accordance with other techniques and standards.

In some embodiments, the radio architecture 105A, 105B may be configured for high-efficiency Wi-Fi (HEW) communications in accordance with the IEEE 802.11ax standard. In these embodiments, the radio architecture 105A, 105B may be configured to communicate in accordance with an OFDMA technique, although the scope of the embodiments is not limited in this respect.

In some other embodiments, the radio architecture 105A, 105B may be configured to transmit and receive signals transmitted using one or more other modulation techniques such as spread spectrum modulation (e.g., direct sequence code division multiple access (DS-CDMA) and/or frequency hopping code division multiple access (FH-CDMA)), time-division multiplexing (TDM) modulation, and/or frequency-division multiplexing (FDM) modulation, although the scope of the embodiments is not limited in this respect.

In some embodiments, the BT baseband circuitry 908 b may be compliant with a Bluetooth (BT) connectivity standard such as Bluetooth, Bluetooth 8.0 or Bluetooth 6.0, or any other iteration of the Bluetooth Standard.

In some embodiments, the radio architecture 105A, 105B may include other radio cards, such as a cellular radio card configured for cellular (e.g., 5GPP such as LTE, LTE-Advanced or 7G communications).

In some IEEE 802.11 embodiments, the radio architecture 105A, 105B may be configured for communication over various channel bandwidths including bandwidths having center frequencies of about 900 MHz, 2.4 GHz, 5 GHz, and bandwidths of about 2 MHz, 4 MHz, 5 MHz, 5.5 MHz, 6 MHz, 8 MHz, 10 MHz, 20 MHz, 40 MHz, 80 MHz (with contiguous bandwidths) or 80+80 MHz (160 MHz) (with non-contiguous bandwidths). In some embodiments, a 920 MHz channel bandwidth may be used. The scope of the embodiments is not limited with respect to the above center frequencies however.

FIG. 10 illustrates WLAN FEM circuitry 904 a in accordance with some embodiments. Although the example of FIG. 10 is described in conjunction with the WLAN FEM circuitry 904 a, the example of FIG. 10 may be described in conjunction with the example BT FEM circuitry 904 b (FIG. 9), although other circuitry configurations may also be suitable.

In some embodiments, the FEM circuitry 904 a may include a TX/RX switch 1002 to switch between transmit mode and receive mode operation. The FEM circuitry 904 a may include a receive signal path and a transmit signal path. The receive signal path of the FEM circuitry 904 a may include a low-noise amplifier (LNA) 1006 to amplify received RF signals 1003 and provide the amplified received RF signals 1007 as an output (e.g., to the radio IC circuitry 906 a-b (FIG. 9)). The transmit signal path of the circuitry 904 a may include a power amplifier (PA) to amplify input RF signals 1009 (e.g., provided by the radio IC circuitry 906 a-b), and one or more filters 1012, such as band-pass filters (BPFs), low-pass filters (LPFs) or other types of filters, to generate RF signals 1015 for subsequent transmission (e.g., by one or more of the antennas 901 (FIG. 9)) via an example duplexer 1014.

In some dual-mode embodiments for Wi-Fi communication, the FEM circuitry 904 a may be configured to operate in either the 2.4 GHz frequency spectrum or the 5 GHz frequency spectrum. In these embodiments, the receive signal path of the FEM circuitry 904 a may include a receive signal path duplexer 1004 to separate the signals from each spectrum as well as provide a separate LNA 1006 for each spectrum as shown. In these embodiments, the transmit signal path of the FEM circuitry 904 a may also include a power amplifier 1010 and a filter 1012, such as a BPF, an LPF or another type of filter for each frequency spectrum and a transmit signal path duplexer 1004 to provide the signals of one of the different spectrums onto a single transmit path for subsequent transmission by the one or more of the antennas 901 (FIG. 9). In some embodiments, BT communications may utilize the 2.4 GHz signal paths and may utilize the same FEM circuitry 904 a as the one used for WLAN communications.

FIG. 11 illustrates radio IC circuitry 906 a in accordance with some embodiments. The radio IC circuitry 906 a is one example of circuitry that may be suitable for use as the WLAN or BT radio IC circuitry 906 a/ 906 b (FIG. 9), although other circuitry configurations may also be suitable. Alternatively, the example of FIG. 11 may be described in conjunction with the example BT radio IC circuitry 906 b.

In some embodiments, the radio IC circuitry 906 a may include a receive signal path and a transmit signal path. The receive signal path of the radio IC circuitry 906 a may include at least mixer circuitry 1102, such as, for example, down-conversion mixer circuitry, amplifier circuitry 1106 and filter circuitry 1108. The transmit signal path of the radio IC circuitry 906 a may include at least filter circuitry 1112 and mixer circuitry 1114, such as, for example, up-conversion mixer circuitry. Radio IC circuitry 906 a may also include synthesizer circuitry 1104 for synthesizing a frequency 1105 for use by the mixer circuitry 1102 and the mixer circuitry 1114. The mixer circuitry 1102 and/or 1114 may each, according to some embodiments, be configured to provide direct conversion functionality. The latter type of circuitry presents a much simpler architecture as compared with standard super-heterodyne mixer circuitries, and any flicker noise brought about by the same may be alleviated for example through the use of OFDM modulation. FIG. 11 illustrates only a simplified version of a radio IC circuitry, and may include, although not shown, embodiments where each of the depicted circuitries may include more than one component. For instance, mixer circuitry 1114 may each include one or more mixers, and filter circuitries 1108 and/or 1112 may each include one or more filters, such as one or more BPFs and/or LPFs according to application needs. For example, when mixer circuitries are of the direct-conversion type, they may each include two or more mixers.

In some embodiments, mixer circuitry 1102 may be configured to down-convert RF signals 1007 received from the FEM circuitry 904 a-b (FIG. 9) based on the synthesized frequency 1105 provided by synthesizer circuitry 1104. The amplifier circuitry 1106 may be configured to amplify the down-converted signals and the filter circuitry 1108 may include an LPF configured to remove unwanted signals from the down-converted signals to generate output baseband signals 1107. Output baseband signals 1107 may be provided to the baseband processing circuitry 908 a-b (FIG. 9) for further processing. In some embodiments, the output baseband signals 1107 may be zero-frequency baseband signals, although this is not a requirement. In some embodiments, mixer circuitry 1102 may comprise passive mixers, although the scope of the embodiments is not limited in this respect.

In some embodiments, the mixer circuitry 1114 may be configured to up-convert input baseband signals 1111 based on the synthesized frequency 1105 provided by the synthesizer circuitry 1104 to generate RF output signals 1009 for the FEM circuitry 904 a-b. The baseband signals 1111 may be provided by the baseband processing circuitry 908 a-b and may be filtered by filter circuitry 1112. The filter circuitry 1112 may include an LPF or a BPF, although the scope of the embodiments is not limited in this respect.

In some embodiments, the mixer circuitry 1102 and the mixer circuitry 1114 may each include two or more mixers and may be arranged for quadrature down-conversion and/or up-conversion respectively with the help of synthesizer 1104. In some embodiments, the mixer circuitry 1102 and the mixer circuitry 1114 may each include two or more mixers each configured for image rejection (e.g., Hartley image rejection). In some embodiments, the mixer circuitry 1102 and the mixer circuitry 1114 may be arranged for direct down-conversion and/or direct up-conversion, respectively. In some embodiments, the mixer circuitry 1102 and the mixer circuitry 1114 may be configured for super-heterodyne operation, although this is not a requirement.

Mixer circuitry 1102 may comprise, according to one embodiment: quadrature passive mixers (e.g., for the in-phase (I) and quadrature phase (Q) paths). In such an embodiment, RF input signal 1007 from FIG. 11 may be down-converted to provide I and Q baseband output signals to be sent to the baseband processor

Quadrature passive mixers may be driven by zero and ninety-degree time-varying LO switching signals provided by a quadrature circuitry which may be configured to receive a LO frequency (fLO) from a local oscillator or a synthesizer, such as LO frequency 1105 of synthesizer 1104 (FIG. 11). In some embodiments, the LO frequency may be the carrier frequency, while in other embodiments, the LO frequency may be a fraction of the carrier frequency (e.g., one-half the carrier frequency, one-third the carrier frequency). In some embodiments, the zero and ninety-degree time-varying switching signals may be generated by the synthesizer, although the scope of the embodiments is not limited in this respect.

In some embodiments, the LO signals may differ in duty cycle (the percentage of one period in which the LO signal is high) and/or offset (the difference between start points of the period). In some embodiments, the LO signals may have an 85% duty cycle and an 80% offset. In some embodiments, each branch of the mixer circuitry (e.g., the in-phase (I) and quadrature phase (Q) path) may operate at an 80% duty cycle, which may result in a significant reduction is power consumption.

The RF input signal 1007 (FIG. 10) may comprise a balanced signal, although the scope of the embodiments is not limited in this respect. The I and Q baseband output signals may be provided to low-noise amplifier, such as amplifier circuitry 1106 (FIG. 11) or to filter circuitry 1108 (FIG. 11).

In some embodiments, the output baseband signals 1107 and the input baseband signals 1111 may be analog baseband signals, although the scope of the embodiments is not limited in this respect. In some alternate embodiments, the output baseband signals 1107 and the input baseband signals 1111 may be digital baseband signals. In these alternate embodiments, the radio IC circuitry may include analog-to-digital converter (ADC) and digital-to-analog converter (DAC) circuitry.

In some dual-mode embodiments, a separate radio IC circuitry may be provided for processing signals for each spectrum, or for other spectrums not mentioned here, although the scope of the embodiments is not limited in this respect.

In some embodiments, the synthesizer circuitry 1104 may be a fractional-N synthesizer or a fractional N/N+1 synthesizer, although the scope of the embodiments is not limited in this respect as other types of frequency synthesizers may be suitable. For example, synthesizer circuitry 1104 may be a delta-sigma synthesizer, a frequency multiplier, or a synthesizer comprising a phase-locked loop with a frequency divider. According to some embodiments, the synthesizer circuitry 1104 may include digital synthesizer circuitry. An advantage of using a digital synthesizer circuitry is that, although it may still include some analog components, its footprint may be scaled down much more than the footprint of an analog synthesizer circuitry. In some embodiments, frequency input into synthesizer circuity 1104 may be provided by a voltage controlled oscillator (VCO), although that is not a requirement. A divider control input may further be provided by either the baseband processing circuitry 908 a-b (FIG. 9) depending on the desired output frequency 1105. In some embodiments, a divider control input (e.g., N) may be determined from a look-up table (e.g., within a Wi-Fi card) based on a channel number and a channel center frequency as determined or indicated by the example application processor 910. The application processor 910 may include, or otherwise be connected to, one of the example secure signal converter 101 or the example received signal converter 103 (e.g., depending on which device the example radio architecture is implemented in).

In some embodiments, synthesizer circuitry 1104 may be configured to generate a carrier frequency as the output frequency 1105, while in other embodiments, the output frequency 1105 may be a fraction of the carrier frequency (e.g., one-half the carrier frequency, one-third the carrier frequency). In some embodiments, the output frequency 1105 may be a LO frequency (fLO).

FIG. 12 illustrates a functional block diagram of baseband processing circuitry 908 a in accordance with some embodiments. The baseband processing circuitry 908 a is one example of circuitry that may be suitable for use as the baseband processing circuitry 908 a (FIG. 9), although other circuitry configurations may also be suitable. Alternatively, the example of FIG. 11 may be used to implement the example BT baseband processing circuitry 908 b of FIG. 9.

The baseband processing circuitry 908 a may include a receive baseband processor (RX BBP) 1202 for processing receive baseband signals 1109 provided by the radio IC circuitry 906 a-b (FIG. 9) and a transmit baseband processor (TX BBP) 1204 for generating transmit baseband signals 1111 for the radio IC circuitry 906 a-b. The baseband processing circuitry 908 a may also include control logic 1206 for coordinating the operations of the baseband processing circuitry 908 a.

In some embodiments (e.g., when analog baseband signals are exchanged between the baseband processing circuitry 908 a-b and the radio IC circuitry 906 a-b), the baseband processing circuitry 908 a may include ADC 1210 to convert analog baseband signals 1209 received from the radio IC circuitry 906 a-b to digital baseband signals for processing by the RX BBP 1202. In these embodiments, the baseband processing circuitry 908 a may also include DAC 1212 to convert digital baseband signals from the TX BBP 1204 to analog baseband signals 1211.

In some embodiments that communicate OFDM signals or OFDMA signals, such as through baseband processor 908 a, the transmit baseband processor 1204 may be configured to generate OFDM or OFDMA signals as appropriate for transmission by performing an inverse fast Fourier transform (IFFT). The receive baseband processor 1202 may be configured to process received OFDM signals or OFDMA signals by performing an FFT. In some embodiments, the receive baseband processor 1202 may be configured to detect the presence of an OFDM signal or OFDMA signal by performing an autocorrelation, to detect a preamble, such as a short preamble, and by performing a cross-correlation, to detect a long preamble. The preambles may be part of a predetermined frame structure for Wi-Fi communication.

Referring back to FIG. 9, in some embodiments, the antennas 901 (FIG. 9) may each comprise one or more directional or omnidirectional antennas, including, for example, dipole antennas, monopole antennas, patch antennas, loop antennas, microstrip antennas or other types of antennas suitable for transmission of RF signals. In some multiple-input multiple-output (MIMO) embodiments, the antennas may be effectively separated to take advantage of spatial diversity and the different channel characteristics that may result. Antennas 901 may each include a set of phased-array antennas, although embodiments are not so limited.

Although the radio architecture 105A, 105B is illustrated as having several separate functional elements, one or more of the functional elements may be combined and may be implemented by combinations of software-configured elements, such as processing elements including digital signal processors (DSPs), and/or other hardware elements. For example, some elements may comprise one or more microprocessors, DSPs, field-programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), radio-frequency integrated circuits (RFICs) and combinations of various hardware and logic circuitry for performing at least the functions described herein. In some embodiments, the functional elements may refer to one or more processes operating on one or more processing elements. 

What is claimed is:
 1. A multi-link device (MLD), the MLD comprising processing circuitry coupled to storage, the processing circuitry configured to: generate a first traffic indication map (TIM) comprising a first bitmap comprising a first indication that traffic is to be sent by a first access point (AP) device of the MLD to a first non-AP device of a second MLD during a beacon interval occurring after a beacon using a first communication link between the first AP device of the MLD and the first non-AP device of the second MLD; generate a second TIM comprising a second bitmap comprising a second indication that no traffic is to be sent by a second AP device of the MLD to a second non-AP device of the second MLD during the beacon interval using a second communication link between the second AP device of the MLD and the second non-AP device of the second MLD; cause to send, using the first AP device of the MLD and the first communication link, the beacon, the beacon comprising the first TIM and the second TIM; and cause to send, using the first AP device of the MLD and the first communication link, a data frame to the first non-AP device of the second MLD during the beacon interval.
 2. The MLD of claim 1, wherein the processing circuitry is further configured to: generate a third TIM comprising a third bitmap comprising a third indication that no traffic is to be sent by the first AP device of the MLD to the first non-AP device of the second MLD during a second beacon interval occurring after a second beacon using the first communication link; generate a fourth TIM comprising a fourth bitmap comprising a fourth indication that traffic is to be sent by the second AP device of the MLD to the second non-AP device of the second MLD during the second beacon interval using the second communication link; cause to send, using the first AP device of the MLD and the first communication link, the second beacon, the second beacon comprising the first TIM and the second TIM; and cause to send, using the first AP device of the MLD and the first communication link, a data frame to the first non-AP device of the second MLD during the second beacon interval.
 3. The MLD of claim 2, wherein: a first link identifier indicative of the first communication link is absent from the first TIM and the third TIM, the second TIM comprises a second link identifier indicative of the second communication link, and the fourth TIM comprises the second link identifier.
 4. The MLD of claim 1, wherein the second indication is associated with a doze state for the second non-AP device during the beacon interval.
 5. The MLD of claim 1, wherein the first indication is a first bit associated with an association identifier for the first non-AP device of the second MLD, and wherein the second indication is a second bit associated with the association identifier for the first non-AP device of the second MLD.
 6. The MLD of claim 1, wherein the processing circuitry is further configured to: generate a third TIM comprising a third bitmap comprising a third indication that no traffic is to be sent by a third AP device of the MLD to a third non-AP device of the second MLD during the beacon interval using a third communication link between the third AP device of the MLD and the third non-AP device of the second MLD, wherein the beacon further comprises the third TIM.
 7. The MLD of claim 1, wherein the processing circuitry is further configured to cause to send a second beacon using the second AP device of the MLD and the second communication link during the beacon interval.
 8. The MLD of claim 1, further comprising a transceiver configured to transmit and receive wireless signals comprising at least one of the beacon or the data frame.
 9. The MLD of claim 8, further comprising an antenna coupled to the transceiver to cause to send the wireless signals.
 10. A non-transitory computer-readable medium storing computer-executable instructions which when executed by one or more processors result in performing operations comprising: identifying, by a first non-access point (AP) device of a first MLD, a beacon received from a first AP device of a second MLD using a first communication link between the first non-AP device of the first MLD and the first AP device of the second MLD; identifying, by the first MLD, a first traffic indication map (TIM) in the beacon, the first TIM comprising a first bitmap comprising a first indication that traffic is to be sent by the first AP device of the second MLD to the first non-AP device of the first MLD during a beacon interval occurring after the beacon using the first communication link; identifying, by the first MLD, a second TIM in the beacon, the second TIM comprising a second bitmap comprising a second indication that no traffic is to be sent by a second AP device of the second MLD to a second non-AP device of the first MLD during the beacon interval using a second communication link between the second AP device of the second MLD and the second non-AP device of the first MLD; causing, by the first MLD, the second non-AP device of the first MLD to enter a doze state during the beacon interval; and identifying, by the first MLD, a data frame received during the beacon interval from the first AP device of the second MLD using the first communication link.
 11. The non-transitory computer-readable medium of claim 10, the operations further comprising: identifying, by the first MLD, a second beacon received from the first AP device of the second MLD using the first communication link; identifying, by the first MLD, a third TIM in the second beacon, the third TIM comprising a third bitmap comprising a third indication that no traffic is to be sent by the first AP device of the second MLD to the first non-AP device of the first MLD during a second beacon interval occurring after the second beacon using the first communication link; identifying, by the first MLD, a fourth TIM in the second beacon, the fourth TIM comprising a fourth indication that traffic is to be sent by the second AP device of the second MLD to the second non-AP device of the first MLD during the second beacon interval using the second communication link; causing, by the first MLD, the first non-AP device of the first MLD to enter a doze state during the second beacon interval; and identifying, by the first MLD, a data frame received during the second beacon interval from the second AP device of the second MLD using the first communication link.
 12. The non-transitory computer-readable medium of claim 11, wherein: a first link identifier indicative of the first communication link is absent from the first TIM and the third TIM, the second TIM comprises a second link identifier indicative of the second communication link, and the fourth TIM comprises the second link identifier.
 13. The non-transitory computer-readable medium of claim 10, wherein the first indication is a first bit associated with an association identifier for the first non-AP device of the first MLD, and wherein the second indication is a second bit associated with the association identifier for the first non-AP device of the first MLD.
 14. The non-transitory computer-readable medium of claim 10, the operations further comprising: identifying, by the first MLD, a third TIM in the beacon, the third TIM comprising a third bitmap comprising a third indication that no traffic is to be sent by a third AP device of the second MLD to a third non-AP device of the first MLD during the beacon interval using a third communication link between the third AP device of the second MLD and the third non-AP device of the first MLD; and causing, by the first MLD, the third non-AP device of the first MLD to enter a doze state during the beacon interval.
 15. A method for indicating traffic using multi-link devices (MLDs), the method comprising: generating, by processing circuitry of a first MLD, a first traffic indication map (TIM) comprising a first bitmap comprising a first indication that traffic is to be sent by a first access point (AP) device of the first MLD to a first non-AP device of a second MLD during a beacon interval occurring after a beacon using a first communication link between the first AP device of the first MLD and the first non-AP device of the second MLD; generating, by the processing circuitry, a second TIM comprising a second bitmap comprising a second indication that no traffic is to be sent by a second AP device of the first MLD to a second non-AP device of the second MLD during the beacon interval using a second communication link between the second AP device of the first MLD and the second non-AP device of the second MLD; causing to send, by the processing circuitry, using the first AP device of the first MLD and the first communication link, the beacon, the beacon comprising the first TIM and the second TIM; and causing to send, by the processing circuitry, using the first AP device of the first MLD and the first communication link, a data frame to the first non-AP device of the second MLD during the beacon interval.
 16. The method of claim 15, further comprising: generating a third TIM comprising a third bitmap comprising a third indication that no traffic is to be sent by the first AP device of the first MLD to the first non-AP device of the second MLD during a second beacon interval occurring after a second beacon using the first communication link; generating a fourth TIM comprising a fourth bitmap comprising a fourth indication that traffic is to be sent by the second AP device of the first MLD to the second non-AP device of the second MLD during the second beacon interval using the second communication link; causing to send, using the first AP device of the first MLD and the first communication link, the second beacon, the second beacon comprising the first TIM and the second TIM; and cause to send, using the first AP device of the first MLD and the first communication link, a data frame to the first non-AP device of the second MLD during the second beacon interval.
 17. The method of claim 16, wherein: a first link identifier indicative of the first communication link is absent from the first TIM and the third TIM, the second TIM comprises a second link identifier indicative of the second communication link, and the fourth TIM comprises the second link identifier.
 18. The method of claim 15, wherein the second indication is associated with a doze state for the second non-AP device during the beacon interval.
 19. The method of claim 15, wherein the first indication is a first bit associated with an association identifier for the first non-AP device of the second MLD, and wherein the second indication is a second bit associated with the association identifier for the first non-AP device of the second MLD.
 20. The method of claim 15, further comprising: generating a third TIM comprising a third bitmap comprising a third indication that no traffic is to be sent by a third AP device of the first MLD to a third non-AP device of the second MLD during the beacon interval using a third communication link between the third AP device of the first MLD and the third non-AP device of the second MLD, wherein the beacon further comprises the third TIM. 